Repository navigation
chore: organize relay docs and deployment artifacts - #119
Merged
Merged
Conversation
abruption
force-pushed
the
chore/111-organize-relay-docs
branch
from
September 21, 2026 05:35
50d3092 to
5ac1846
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The completed relay69 prototype remained alongside the production relay, while reusable service examples and the deployed KR reference shared one flat directory. This change removes the obsolete prototype source after porting its unique protocol and security regressions to the product suite, and separates reusable examples from instance-specific operations.
It also adds audience-based documentation indexes in English, Korean, Japanese, and Simplified Chinese, updates every moved link, and makes sdist contents explicit: current docs and reusable examples are included; prototype source, local build output, and KR operational files are excluded.
Validation:
python -m unittest discover -s tests -v(423 passed, 5 optional/platform skips)SESSION_PEER_CONTROL_INTEGRATION=1 python -m unittest tests.test_control_integration -v(5 passed)npm ci && npm run typecheck && npm test && npm audit --omit=devincontrol/(69 passed, audit 0)git diff --checkCloses #111